Mobile tele-presence system with a microphone system

ABSTRACT

A remote controlled robot system that includes a robot and a remote control station. The robot includes a binaural microphone system that is coupled to a speaker system of the remote control station. The binaural microphone system may include a pair of microphones located at opposite sides of a robot head. the location of the microphones roughly coincides with the location of ears on a human body. Such microphone location creates a mobile robot that more effectively simulates the tele-presence of an operator of the system. The robot may include two different microphone systems and the ability to switch between systems. For example, the robot may also include a zoom camera system and a directional microphone. The directional microphone may be utilized to capture sound from a direction that corresponds to an object zoomed upon by the camera system.

CROSS-REFERENCE TO RELATED APPLICATION

This is a continuation of U.S. application Ser. No. 12/148,464 filedApr. 17, 2008 now U.S. Pat. No. 8,170,241.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The subject matter disclosed generally relates to the field of mobiletwo-way teleconferencing.

2. Background Information

Robots have been used in a variety of applications ranging from remotecontrol of hazardous material to assisting in the performance ofsurgery. For example, U.S. Pat. No. 5,762,458 issued to Wang et al.discloses a system that allows a surgeon to perform minimally invasivemedical procedures through the use of robotically controlledinstruments. One of the robotic arms in the Wang system moves anendoscope that has a camera. The camera allows a surgeon to view asurgical area of a patient.

Tele-robots such as hazardous waste handlers and bomb detectors maycontain a camera that allows the operator to view the remote site. U.S.Pat. No. 6,914,622 issued to Smith et al. and assigned to Telbotics,Inc. (“Telbotics patent”) discloses a teleconferencing platform that hasboth a camera and a monitor. The platform includes mechanisms to bothpivot and raise the camera and the monitor. The Telbotics patent has amicrophone and a system that automatically swivels the monitor to theorigin of sound so that the user's image as displayed by the robotmonitor faces a speaker.

There has been marketed a mobile robot introduced by InTouchTechnologies, Inc., the assignee of this application, under thetrademarks COMPANION and RP-7. The InTouch robot is controlled by a userat a remote station. The remote station may be a personal computer witha joystick that allows the user to remotely control the movement of therobot. Both the robot and remote station have cameras, monitors,speakers and microphones to allow for two-way video/audio communication.The robot camera provides video images to a screen at the remote stationso that the user can view the robot's surroundings and move the robotaccordingly. It would be desirable to create a microphone system thatmore closely simulated sound perceived by human errors so that the userexperiences a more realistic auditory presence through the robot.

BRIEF SUMMARY OF THE INVENTION

A remote controlled robot system that includes a robot and a remotecontrol station. The robot includes a monitor and a binaural microphonesystem. The remote control station includes a speaker system coupled tothe binaural microphone system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a robotic system;

FIG. 1A is an illustration showing the relationship of two microphonesrelative to a monitor of a robot head;

FIG. 2 is a schematic of an electrical system of a robot;

FIG. 3 is a graphical user interface of a remote station.

DETAILED DESCRIPTION

Disclosed is a remote controlled robot system that includes a robot anda remote control station. The robot includes a binaural microphonesystem that is coupled to a speaker system of the remote controlstation. The binaural microphone system may include a pair ofmicrophones located at opposite sides of a robot head. The location ofthe microphones roughly coincides with the location of ears on a humanbody. Such microphone location provides the remote operator with arealistic auditory presence including directionality and distance, as ifthe operator were actually present at the robot location. The robot mayinclude two different microphone systems and the ability to switchbetween systems. For example, the robot may also include a zoom camerasystem and a directional microphone. The directional microphone may beutilized to capture sound from a direction that corresponds to an objectzoomed upon by the camera system.

Referring to the drawings more particularly by reference numbers, FIG. 1shows a robotic system 10 that can be used to conduct a remote visit.The robotic system 10 includes a robot 12, a base station 14 and aremote control station 16. The remote control station 16 may be coupledto the base station 14 through a network 18. By way of example, thenetwork 18 may be either a packet switched network such as the Internet,or a circuit switched network such has a Public Switched TelephoneNetwork (PSTN) or other broadband system. The base station 14 may becoupled to the network 18 by a modem 20 or other broadband networkinterface device. By way of example, the base station 14 may be awireless router. Alternatively, the robot 12 may have a directconnection to the network thru for example a satellite.

The remote control station 16 may include a computer 22 that has amonitor 24, a camera 26, a microphone 28 and a speaker 30. The station16 may also include a headset 31 that can be worn by the user. Thecomputer 22 may have an input device 32 such as a joystick and/or amouse and a keyboard 33. The control station 16 is typically located ina place that is remote from the robot 12. Although only one remotecontrol station 16 is shown, the system 10 may include a plurality ofremote stations. In general any number of robots 12 may be controlled byany number of remote stations 16 or other robots 12. For example, oneremote station 16 may be coupled to a plurality of robots 12, or onerobot 12 may be coupled to a plurality of remote stations 16, or aplurality of robots 12.

Each robot 12 includes a movement platform 34 that is attached to arobot housing 36. As shown in FIG. 2 each robot 12 may include a monitor40 that display an image of the operator at the remote control station.The monitor 40 may be part of a robot head 42 that moves relative to themovement platform 34. The head 42 may have a speaker system 44 thatgenerates sound provided by the remote control station.

The robot 12 includes a binaural microphone system 46. The binauralmicrophone system 46 includes a first microphone 48 located on one sideof the head and a second microphone 50 located on another side of thehead. The microphones 48 and 50 are located at positions approximatelysimilar to the location of ears on a human body. By way of example, themicrophones 48 and 50 can be located about 18 centimeters apart.Utilizing a binaural microphone system 46 creates a robot head thatapproximates a human head. By way of example, the binaural microphonesystem 46 may be a matched pair of omni-directional electric condensermicrophones. One definition of binaural is that the microphones 48 and50 are located at positions at approximately equal angles relative to aplane that intersects and is essentially perpendicular to the camerasystem which is incident with the monitor 40 as shown in FIG. 1A (e.g.θ₁=θ₂).

A matched pair of microphones produce an equal voltage for a given soundpressure. The output signals of the microphones may be processed toproduce stereo audio channels. An example of a matched microphone systemis a product sold by Sound Professionals under the product designationSP-BMC-12. The speaker system of the remote control station may includeheadphones as shown in FIG. 1.

The robot 12 may also have a directional microphone 52. The directionalmicrophone 52 can be used to capture sound received in a certaindirection(s). For example, the directional microphone 52 may be abarrel-like structure that captures sound traveling along a desired axisbut impedes off-axis sound. An example, of such a directional microphoneis a product sold by Sennheiser under the product designation ME66/K6.

The robot 12 has a camera system. The camera system may include a firstcamera 54 and a second camera 56. The second camera 56 may include azoom len(s) and is utilized when the system is in a zoom mode. The firstcamera 54 may provide images in a non-zoom mode. The system can beconfigured so that the sound captured by the directional microphone isthe sole or primary sound recreated at the remote control station.Although two cameras are shown and described, it is to be understoodthat the robot may contain only one camera that has the capability toprovide a zoom image and a non-zoom image.

The robot 12 may also have an antenna 58 that is wirelessly coupled toan antenna 60 of the base station 14. The system 10 allows a user at theremote control station 16 to move the robot 12 through operation of theinput device 32. The robot cameras 54 and 56 are coupled to the remotemonitor 24 so that a user at the remote station 16 can view a patient.Likewise, the robot monitor 40 is coupled to the remote camera 26 sothat the patient can view the user. The microphones 28 and 48, 50 and52, and speakers 30 and 44, allow for audible communication between thepatient and the user.

The remote station computer 22 may operate Microsoft OS software andWINDOWS XP or other operating systems such as LINUX. The remote computer22 may also operate a video driver, a camera driver, an audio driver anda joystick driver. The video images may be transmitted and received withcompression software such as MPEG CODEC.

FIG. 2 shows an embodiment of a robot 12. Each robot 12 may include ahigh level control system 70. The high level control system 50 mayinclude a processor 72 that is connected to a bus 74. The bus 74 iscoupled to the cameras 54 and 56 by an input/output (I/O) ports 76 and78, respectively. The monitor 40 is coupled to the bus 74 by a serialoutput port 80 and a VGA driver 82. The monitor 40 may include atouchscreen function that allows the patient to enter input by touchingthe monitor screen.

The microphones 48, 50 and 52 are coupled to the bus 74 by digital toanalog converters 84, 86 and 88, respectively. The speaker 44 is coupledto the bus 74 by an analog to digital converter 90. The high levelcontroller 70 may also contain random access memory (RAM) device 92, anon-volatile RAM device 94 and a mass storage device 96 that are allcoupled to the bus 74. The mass storage device 96 may contain medicalfiles of the patient that can be accessed by the user at the remotecontrol station 16. For example, the mass storage device 96 may containa picture of the patient. The user, particularly a health care provider,can recall the old picture and make a side by side comparison on themonitor 24 with a present video image of the patient provided by thecamera 38. The robot antennae 58 may be coupled to a wirelesstransceiver 98. By way of example, the transceiver 98 may transmit andreceive information in accordance with IEEE 802.11b.

The controller 70 may operate with a LINUX OS operating system. Thecontroller 70 may also operate MS WINDOWS along with video, camera andaudio drivers for communication with the remote control station 16.Video information may be transceived using MPEG CODEC compressiontechniques. The software may allow the user to send e-mail to thepatient and vice versa, or allow the patient to access the Internet. Ingeneral the high level controller 50 operates to control communicationbetween the robot 12 and the remote control station 16.

The remote control station 16 may include a computer that is similar tothe high level controller 50. The computer would have a processor,memory, I/O, software, firmware, etc. for generating, transmitting,receiving and processing information.

The high level controller 70 may be linked to a low level controller 100by a serial port 102. The low level controller 100 runs softwareroutines that mechanically actuate the robot 12. For example, the lowlevel controller 100 provides instructions to actuate the movementplatform to move the robot 12. The low level controller 52 may receivemovement instructions from the high level controller 70. The movementinstructions may be received as movement commands from the remotecontrol station or another robot. Although two controllers are shown, itis to be understood that each robot 12 may have one controller, or morethan two controllers, controlling the high and low level functions.

The robot 12 may have mechanisms so that the monitor 40, cameras 56 and58 and microphones 48, 50 and 52 all move together in at least twodegrees of freedom. Moving the microphones with the cameras insures thatthe microphone system provides stereophonic sound for all robot headpositions. The system may be the same or similar to a robotic systemprovided by the assignee InTouch-Health, Inc. of Santa Barbara, Calif.under the name RP-6. The system may also be the same or similar to thesystem disclosed in U.S. Pat. No. 7,158,859 that issued on Jan. 2, 2007,which is hereby incorporated by reference.

FIG. 3 shows a display user interface (“DUI”) 120 that can be displayedat the remote station 16. The DUI 120 may include a robot view field 122that displays a video image provided by the camera of the robot. The DUI120 may also include a station view field 124 that displays a videoimage provided by the camera of the remote station 16. The DUI 120 maybe part of an application program stored and operated by the computer 22of the remote station 16.

The DUI 120 can include graphical icons 126 and 128 that allow the userto switch between the directional microphone and binaural microphonesystem, respectively. The DUI 120 may include a graphical overlay 130 inthe robot view field 122 that indicates an origin of sound. The positionof the overlay 130 corresponds to the sound origin. For example, theposition of the overlay 130 shown in FIG. 3 indicates that the origin ofsound is to the left of the robot. The user can then move the robotaccordingly to improve the volume heard by the microphone system.

The origin of sound can be determined by initially looking at the timeof difference between the arrival of sound to both microphones 48 and50. The peak time t_(d) can be found in the correlation functionC_(1,2)(t)=X₁(i)*X₂(i+t) for all i. An estimate for the angle of arrival(a) can be computed from the trig function a=arcsin(v*t_(d)/d_(1,2))where d_(1,2) is the distance between microphones and v is the velocityof sound.

The system may have an automatic mode such that sound captured by thebinaural microphone system is reproduced by the remote station when thecamera system is in a non-zoom mode and sound captured by thedirectional microphone is reproduced by the station when the camerasystem is in a zoom mode. The user can switch between automatic andmanual modes by selecting an icon (not shown). A letter “A” may appearadjacent to the icon when the system is in automatic mode. A letter “M”may appear when the system is in the manual mode.

In operation, the robot 12 may be placed in a home or a facility whereone or more patients are to be monitored and/or assisted. The facilitymay be a hospital or a residential care facility. By way of example, therobot 12 may be placed in a home where a health care provider maymonitor and/or assist the patient. Likewise, a friend or family membermay communicate with the patient. The cameras and monitors at both therobot and remote control stations allow for teleconferencing between thepatient and the person at the remote station(s).

The robot 12 can be maneuvered through the home or a facility bymanipulating the input device 32 at a remote station 16. The robot 10may be controlled by a number of different users. To accommodate forthis the robot may have an arbitration system. The arbitration systemmay be integrated into the operating system of the robot 12. Forexample, the arbitration technique may be embedded into the operatingsystem of the high-level controller 50.

By way of example, the users may be divided into classes that includethe robot itself, a local user, a caregiver, a doctor, a family member,or a service provider. The robot 12 may override input commands thatconflict with robot operation. For example, if the robot runs into awall, the system may ignore all additional commands to continue in thedirection of the wall. A local user is a person who is physicallypresent with the robot. The robot could have an input device that allowslocal operation. For example, the robot may incorporate a voicerecognition system that receives and interprets audible commands.

A caregiver is someone who remotely monitors the patient. A doctor is amedical professional who can remotely control the robot and also accessmedical files contained in the robot memory. The family and serviceusers remotely access the robot. The service user may service the systemsuch as by upgrading software, or setting operational parameters.

The robot 12 may operate in one of two different modes; an exclusivemode, or a sharing mode. In the exclusive mode only one user has accesscontrol of the robot. The exclusive mode may have a priority assigned toeach type of user. By way of example, the priority may be in order oflocal, doctor, caregiver, family and then service user. In the sharingmode two or more users may share access with the robot. For example, acaregiver may have access to the robot, the caregiver may then enter thesharing mode to allow a doctor to also access the robot. Both thecaregiver and the doctor can conduct a simultaneous tele-conference withthe patient.

The arbitration scheme may have one of four mechanisms; notification,timeouts, queue and call back. The notification mechanism may informeither a present user or a requesting user that another user has, orwants, access to the robot. The timeout mechanism gives certain types ofusers a prescribed amount of time to finish access to the robot. Thequeue mechanism is an orderly waiting list for access to the robot. Thecall back mechanism informs a user that the robot can be accessed. Byway of example, a family user may receive an e-mail message that therobot is free for usage. Tables I and II, show how the mechanismsresolve access request from the various users.

TABLE I Access Medical Command Software/Debug Set User Control RecordOverride Access Priority Robot No No Yes (1) No No Local No No Yes (2)No No Caregiver Yes Yes Yes (3) No No Doctor No Yes No No No Family NoNo No No No Service Yes No Yes Yes Yes

TABLE II Requesting User Local Caregiver Doctor Family Service CurrentLocal Not Allowed Warn current user of Warn current user of Warn currentuser of Warn current user of User pending user pending user pending userpending user Notify requesting user Notify requesting user Notifyrequesting user Notify requesting user that system is in use that systemis in use that system is in use that system is in use Set timeout Settimeout = 5 m Set timeout = 5 m No timeout Call back Call back CaregiverWarn current user of Not Allowed Warn current user of Warn current userof Warn current user of pending user. pending user pending user pendinguser Notify requesting user Notify requesting user Notify requestinguser Notify requesting user that system is in use. that system is in usethat system is in use that system is in use Release control Set timeout= 5 m Set timeout = 5 m No timeout Queue or callback Callback DoctorWarn current user of Warn current user of Warn current user of Notifyrequesting user Warn current user of pending user pending user pendinguser that system is in use pending user Notify requesting user Notifyrequesting user Notify requesting user No timeout Notify requesting userthat system is in use that system is in use that system is in use Queueor callback that system is in use Release control Set timeout = 5 m Notimeout No timeout Callback Callback Family Warn current user of Notifyrequesting user Warn current user of Warn current user of Warn currentuser of pending user that system is in use pending user pending userpending user Notify requesting user No timeout Notify requesting userNotify requesting user Notify requesting user that system is in use Putin queue or that system is in use that system is in use that system isin use Release Control callback Set timeout = 1 m Set timeout = 5 m Notimeout Queue or callback Callback Service Warn current user of Notifyrequesting user Warn current user of Warn current user of Not Allowedpending user that system is in use request pending user Notifyrequesting user No timeout Notify requesting user Notify requesting userthat system is in use Callback that system is in use that system is inuse No timeout No timeout No timeout Callback Queue or callback

The information transmitted between the station 16 and the robot 12 maybe encrypted. Additionally, the user may have to enter a password toenter the system 10. A selected robot is then given an electronic key bythe station 16. The robot 12 validates the key and returns another keyto the station 16. The keys are used to encrypt information transmittedin the session.

The robot 12 and remote station 16 transmit commands through thebroadband network 18. The commands can be generated by the user in avariety of ways. For example, commands to move the robot may begenerated by moving the joystick 32 (see FIG. 1). The commands arepreferably assembled into packets in accordance with TCP/IP protocol.Table III provides a list of control commands that are generated at theremote station and transmitted to the robot through the network.

TABLE III Control Commands Command Example Description drive drive 10.00.0 5.0 The drive command directs the robot to move at the specifiedvelocity (in cm/sec) in the (x, y) plane, and turn its facing at thespecified rate (degrees/sec). goodbye goodbye The goodbye commandterminates a user session and relinquishes control of the robotgotoHomePosition gotoHomePosition 1 The gotoHomePosition command movesthe head to a fixed “home” position (pan and tilt), and restores zoom todefault value. The index value can be 0, 1, or 2. The exact pan/tiltvalues for each index are specified in robot configuration files. headhead vel pan 5.0 tilt The head command controls the head motion. 10.0 Itcan send commands in two modes, identified by keyword: either positional(“pos”) or velocity (“vol”). In velocity mode, the pan and tilt valuesare desired velocities of the head on the pan and tilt axes, indegree/sec. A single command can include just the pan section, or justthe tilt section, or both. keepalive keepalive The keepalive commandcauses no action, but keeps the communication (socket) link open so thata session can continue. In scripts, it can be used to introduce delaytime into the action. odometry odometry 5 The odometry command enablesthe flow of odometry messages from the robot. The argument is the numberof times odometry is to be reported each second. A value of 0 turnsodometry off. reboot reboot The reboot command causes the robot computerto reboot immediately. The ongoing session is immediately broken off.restoreHeadPosition restoreHeadPosition The restoreHeadPositionfunctions like the gotoHomePosition command, but it homes the head to aposition previously saved with gotoHomePosition. saveHeadPositionsaveHeadPosition The saveHeadPosition command causes the robot to savethe current head position (pan and tilt) in a scratch location intemporary storage so that this position can be restored. Subsequentcalls to “restoreHeadPosition” will restore this saved position. Eachcall to saveHeadPosition overwrites any previously saved position.setCameraFocus setCameraFocus 100.0 The setCameraFocus command controlsfocus for the camera on the robot side. The value sent is passed “raw”to the video application running on the robot, which interprets itaccording to its own specification. setCameraZoom setCameraZoom 100.0The setCameraZoom command controls zoom for the camera on the robotside. The value sent is passed “raw” to the video application running onthe robot, which interprets it according to its own specification.shutdown Shutdown The shutdown command shuts down the robot and powersdown its computer. stop stop The stop command directs the robot to stopmoving immediately. It is assumed this will be as sudden a stop as themechanism can safely accommodate. timing Timing 3245629 500 The timingmessage is used to estimate message latency. It holds the UCT value(seconds + milliseconds) of the time the message was sent, as recordedon the sending machine. To do a valid test, you must compare results ineach direction (i.e., sending from machine A to machine B, then frommachine B to machine A) in order to account for differences in theclocks between the two machines. The robot records data internally toestimate average and maximum latency over the course of a session, whichit prints to log files. userTask userTask “Jane Doe” The userTaskcommand notifies the robot of “Remote Visit” the current user and task.It typically is sent once at the start of the session, although it canbe sent during a session if the user and/or task change. The robot usesthis information for record-keeping.

Table IV provides a list of reporting commands that are generated by therobot and transmitted to the remote station through the network.

TABLE IV Reporting Commands Command Example Description abnormalExitabnormalExit This message informs the user that the robot software hascrashed or otherwise exited abnormally. Te robot software catches top-level exceptions and generates this message if any such exceptionsoccur. bodyType bodyType 3 The bodyType message informs the stationwhich type body (using the numbering of the mechanical team) the currentrobot has. This allows the robot to be drawn correctly in the stationuser interface, and allows for any other necessary body-specificadjustments. driveEnabled driveEnabled true This message is sent at thestart of a session to indicate whether the drive system is operational.emergencyShutdown emergencyShutdown This message informs the stationthat the robot software has detected a possible “runaway” condition (anfailure causing the robot to move out of control) and is shutting theentire system down to prevent hazardous motion. odometry odometry 10 20340 The odometry command reports the current (x, y) position (cm) andbody orientation (degrees) of the robot, in the original coordinatespace of the robot at the start of the session. sensorGroup group_dataSensors on the robot are arranged into groups, each group of a singletype (bumps, range sensors, charge meter, etc.) The sensorGroup messageis sent once per group at the start of each session. It contains thenumber, type, locations, and any other relevant data for the sensors inthat group. The station assumes nothing about the equipment carried onthe robot; everything it knows about the sensors comes from thesensorGroup messages. sensorState groupName state data The sensorStatecommand reports the current state values for a specified group ofsensor. The syntax and interpretation for the state data is specific toeach group. This message is sent once for each group at each sensorevaluation (normally several times per second). systemError systemErrorThis message informs the station user of a driveController failure inone of the robot's subsystems. The error_type argument indicates whichsubsystem failed, including driveController, sensorController, headHome.systemInfo systemInfo wireless 45 This message allows regular reportingof information that falls outside the sensor system such as wirelesssignal strength. text text “This is some The text string sends a textstring from the text” robot to the station, where the string isdisplayed to the user. This message is used mainly for debugging.version version 1.6 This message identifies the software versioncurrently running on the robot. It is sent once at the start of thesession to allow the station to do any necessary backward compatibilityadjustments.

The processor 72 of the robot high level controller 70 may operate aprogram that determines whether the robot 12 has received a robotcontrol command within a time interval. For example, if the robot 12does not receive a control command within 2 seconds then the processor54 provides instructions to the low level controller 50 to stop therobot 12. Although a software embodiment is described, it is to beunderstood that the control command monitoring feature could beimplemented with hardware, or a combination of hardware and software.The hardware may include a timer that is reset each time a controlcommand is received and generates, or terminates, a command or signal,to stop the robot.

The remote station computer 22 may monitor the receipt of video imagesprovided by the robot camera. The computer 22 may generate and transmita STOP command to the robot if the remote station does not receive ortransmit an updated video image within a time interval. The STOP commandcauses the robot to stop. By way of example, the computer 22 maygenerate a STOP command if the remote control station does not receive anew video image within 2 seconds. Although a software embodiment isdescribed, it is to be understood that the video image monitoringfeature could be implemented with hardware, or a combination of hardwareand software. The hardware may include a timer that is reset each time anew video image is received and generates, or terminates, a command orsignal, to generate the robot STOP command.

The robot may be a robot head that can both pivot and spin the camera 38and the monitor 40. Such a head is described in the '859 patent. Therobot head 350 may be in the system either with or instead of the mobilerobot 12. The robot head can be particularly useful for doctorproctoring. The head can be located at a medical facility such as anemergency room or a doctor's office. A doctor at the remote location canassist in the diagnosis and medical treatment of a patient located atthe robot location. The doctor can move the head to view the patientthrough control commands from the remote control station. Doctorproctoring can also be performed with a mobile robot 12.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other modifications mayoccur to those ordinarily skilled in the art.

What is claimed is:
 1. A remote controlled robot system, comprising: arobot with a robot camera, a robot monitor, a robot microphone, a robotspeaker, and a plurality of robot microphones; and, a remote controlstation that transmits commands to control said robot, said remotecontrol station includes a station camera coupled to said robot monitor,a station monitor coupled to said robot camera, a station microphonecoupled to said robot speaker, and a station speaker system that iscoupled to one or more of said plurality of robot microphones, whereinsaid station monitor displays a display user interface with a graphicalinterface that can be used to switch between said station speaker systemreproducing sound from a first number of said plurality of robotmicrophones or reproducing sound from a second number of said pluralityof robot microphones, wherein both of said first and second numbers aregreater than or equal to one, and said first and second numbers aredifferent.
 2. The system of claim 1, wherein said robot camera and saidplurality of robot microphones are attached to a robot head, saidplurality of robot microphones including a first microphone located on afirst side of said head and a second microphone located on a second sideof said head.
 3. The system of claim 1, wherein said binaural of robotmicrophones system includes a first microphone and a second microphonethat are spaced at approximately equal angles relative to a plane thatintersects said camera system.
 4. The system of claim 1, wherein saidcamera system can switch between zoom and non-zoom modes.
 5. The systemof claim 2, wherein said remote control station monitor displays adisplay user interface, said display user interface provides a graphicaldepiction of an origin of sound.
 6. The system of claim 1, wherein saidrobot includes a mobile platform.
 7. A remote controlled robot system,comprising: a robot with a camera system and a plurality of microphonesystems that move together, said plurality of microphone systemsincludes a first microphone system having a first number of microphonesand a second microphone system having a second number of microphones,said first and second numbers are different; and, a remote controlstation that transmits commands to control said robot, said remotecontrol station includes a speaker system that is coupled to at leastone of said plurality of microphone systems and a monitor coupled tosaid robot camera, wherein said monitor displays a display userinterface, said display user interface includes a graphical interfacethat can be used to switch between said first and second microphonesystems.
 8. The system of claim 7, wherein one of said microphonesystems includes a first microphone located on a first side of saidcamera system and a second microphone located on a second side of saidcamera system.
 9. The system of claim 8, wherein said first and secondmicrophones are spaced at approximately equal angles relative to a planethat intersects said camera system.
 10. The system of claim 7, whereinsaid remote control station monitor displays a display user interface,said display user interface provides a graphical depiction of an originof sound.
 11. The system of claim 7, wherein said robot includes amonitor coupled to a camera of said remote control station.
 12. A methodfor hearing sound produced at a site of a robot, comprising: capturingsound with a number of microphones of a robot that has a camera system;transmitting the sound to a remote control station; producing the soundat the remote control station; and, displaying on a monitor of theremote control station a display user interface, said display userinterface includes a graphical interface that can be used to change thenumber of microphones of the robot from which sound is produced at theremote control station, wherein said number of microphones is at leastone.
 13. The method of claim 12, further comprising switching the camerasystem of the robot between zoom and non-zoom modes.
 14. The method ofclaim 12, further comprising displaying a display user interface on amonitor of the remote control station, the display user interfaceprovides a graphical depiction of an origin of sound.